forked from swc-project/swc-node
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update pnpm to v9 #11
Open
peakon-renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/pnpm-9.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
5 times, most recently
from
April 21, 2024 21:31
4421ff0
to
7e46020
Compare
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
April 24, 2024 14:08
7e46020
to
68e72d7
Compare
peakon-renovate
bot
changed the title
chore(deps): update pnpm to v9
chore(deps): update pnpm to v9 - autoclosed
Apr 24, 2024
peakon-renovate
bot
changed the title
chore(deps): update pnpm to v9 - autoclosed
chore(deps): update pnpm to v9
Apr 24, 2024
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
April 30, 2024 06:09
0da55ec
to
f8c42fe
Compare
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
3 times, most recently
from
May 13, 2024 00:12
0f45c6c
to
371dbba
Compare
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
May 27, 2024 09:35
63be071
to
6cac635
Compare
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
June 5, 2024 13:34
ab0b115
to
b3475e6
Compare
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
June 10, 2024 13:59
b3475e6
to
9d5c649
Compare
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
June 17, 2024 16:33
9d5c649
to
168c323
Compare
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
3 times, most recently
from
July 7, 2024 20:27
6bfaa40
to
c9c2e7f
Compare
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
July 22, 2024 01:14
45db140
to
0e1b142
Compare
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
August 7, 2024 02:41
0e1b142
to
69f340e
Compare
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
August 14, 2024 15:29
69f340e
to
8259176
Compare
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
August 26, 2024 17:00
8a6438e
to
0186012
Compare
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
August 31, 2024 03:35
0186012
to
14c754a
Compare
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
September 9, 2024 15:34
14c754a
to
53ac28a
Compare
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
September 22, 2024 05:09
d96947f
to
cf50b9e
Compare
peakon-renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
October 2, 2024 12:46
cf50b9e
to
fd0b8d9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
8.15.9
->9.12.0
Release Notes
pnpm/pnpm (pnpm)
v9.12.0
: pnpm 9.12Compare Source
Minor Changes
Fix peer dependency resolution dead lock #8570. This change might change some of the keys in the
snapshots
field insidepnpm-lock.yaml
but it should happen very rarely.pnpm outdated
command supports now a--sort-by=name
option for sorting outdated dependencies by package name #8523.Added the ability for
overrides
to remove dependencies by specifying"-"
as the field value #8572. For example, to removelodash
from the dependencies, use this configuration inpackage.json
:Patch Changes
pnpm list --json pkg
showed"private": false
for a private package #8519.libc
that differ frompnpm.supportedArchitectures.libc
are not downloaded #7362.ENOENT
errors caused by runningstore prune
in parallel #8586.pnpm bugs
#8596.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.11.0
: pnpm 9.11Compare Source
Minor Changes
pnpm cache
commands for inspecting the metadata cache #8512.Patch Changes
pnpm deploy
withnode-linker=hoisted
produces an emptynode_modules
directory #6682.pnpm deploy
should work in workspace withshared-workspace-lockfile=false
#8475.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.10.0
: pnpm 9.10Compare Source
Minor Changes
Support for a new CLI flag,
--exclude-peers
, added to thelist
andwhy
commands. When--exclude-peers
is used, peer dependencies are not printed in the results, but dependencies of peer dependencies are still scanned #8506.Added a new setting to
package.json
atpnpm.auditConfig.ignoreGhsas
for ignoring vulnerabilities by their GHSA code #6838.For instance:
Patch Changes
Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.9.0
: pnpm 9.9Compare Source
Minor Changes
Minor breaking change. This change might result in resolving your peer dependencies slightly differently but we don't expect it to introduce issues.
We had to optimize how we resolve peer dependencies in order to fix some infinite loops and out-of-memory errors during peer dependencies resolution.
When a peer dependency is a prod dependency somewhere in the dependency graph (with the same version), pnpm will resolve the peers of that peer dependency in the same way across the subgraph.
For example, we have
react-dom
in the peer deps of theform
andbutton
packages.card
hasreact-dom
andreact
as regular dependencies andcard
is a dependency ofform
.These are the direct dependencies of our example project:
These are the dependencies of card:
When resolving peers, pnpm will not re-resolve
react-dom
forcard
, even thoughcard
shadowsreact@16
from the root withreact@17
. So, all 3 packages (form
,card
, andbutton
) will usereact-dom@16
, which in turn usesreact@16
.form
will usereact@16
, whilecard
andbutton
will usereact@17
.Before this optimization
react-dom@16
was duplicated for thecard
, so thatcard
andbutton
would use areact-dom@16
instance that usesreact@17
.Before the change:
After the change
Patch Changes
pnpm deploy
should write thenode_modules/.modules.yaml
to thenode_modules
directory within the deploy directory #7731.node_modules
if it already points to the right location pnpm/symlink-dir#54.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.8.0
: pnpm 9.8Compare Source
Minor Changes
Added a new command for upgrading pnpm itself when it isn't managed by Corepack:
pnpm self-update
. This command will work, when pnpm was installed via the standalone script from the pnpm installation page #8424.When executed in a project that has a
packageManager
field in itspackage.json
file, pnpm will update its version in thepackageManager
field.Patch Changes
CLI tools installed in the root of the workspace should be added to the PATH, when running scripts and
use-node-version
is set.pnpm setup
should never switch to another version of pnpm.This fixes installation with the standalone script from a directory that has a
package.json
with thepackageManager
field. pnpm was installing the version of pnpm specified in thepackageManager
field due to this issue.Ignore non-string value in the os, cpu, libc fields, which checking optional dependencies #8431.
Remember the state of edit dir, allow running
pnpm patch-commit
the second time without having to re-runpnpm patch
.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.7.1
: pnpm 9.7.1Compare Source
Patch Changes
public-hoist-pattern
andhoist-pattern
via env variables #8339.pnpm setup
no longer creates Batch/Powershell scripts on Linux and macOS #8418.pnpm exec
now supports executionEnv #8356.pnpm
field, add warnings for non-rootpnpm
subfields that aren'texecutionEnv
#8143.patch-commit
in which relative path is rejected #8405.@pnpm/exe
to v20.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.7.0
: pnpm 9.7Compare Source
Minor Changes
Added pnpm version management. If the
manage-package-manager-versions
setting is set totrue
, pnpm will switch to the version specified in thepackageManager
field ofpackage.json
#8363. This is the same field used by Corepack. Example:Added the ability to apply patch to all versions #8337.
If the key of
pnpm.patchedDependencies
is a package name without a version (e.g.pkg
), pnpm will attempt to apply the patch to all versions of the package. Failures will be skipped. If there's only one version ofpkg
installed,pnpm patch pkg
and subsequentpnpm patch-commit $edit_dir
will create an entry namedpkg
inpnpm.patchedDependencies
. And pnpm will attempt to apply this patch to other versions ofpkg
in the future.Change the default edit dir location when running
pnpm patch
from a temporary directory tonode_modules/.pnpm_patches/pkg[@​version]
to allow the code editor to open the edit dir in the same file tree as the main project #8379.Substitute environment variables in config keys #6679.
Patch Changes
pnpm install
should runnode-gyp rebuild
if the project has abinding.gyp
file even if the project doesn't have an install script #8293.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors